@dankcushions Thanks a lot for the replies and for this last tip. I've learned a lot with this thread (core options are always saved if modified in-game, I should not mess with them xD, a way to revert them back to defaults...).
Br,
Dimas.

In case anyone else encounters the same issue, here are my config.txt settings:

# For more options and information see # http://rpf.io/configtxt # Some settings may impact device functionality. See link above for details # uncomment if you get no picture on HDMI for a default "safe" mode #hdmi_safe=1 # uncomment this if your display has a black border of unused pixels visible # and your display can output without overscan disable_overscan=1 # uncomment the following to adjust overscan. Use positive numbers if console # goes off screen, and negative if there is too much border #overscan_left=16 #overscan_right=16 #overscan_top=16 #overscan_bottom=16 # uncomment to force a console size. By default it will be display's size minus # overscan. #framebuffer_width=1280 #framebuffer_height=720 # uncomment if hdmi display is not detected and composite is being output hdmi_force_hotplug=1 hdmi_ignore_edid=0xa5000080 # uncomment to force a specific HDMI mode (this will force VGA) #hdmi_group=2 #hdmi_mode=4 # THE ABOVE ARE WORKING, USE AS FALLBACK hdmi_group=1 hdmi_mode=16 # uncomment to force a HDMI mode rather than DVI. This can make audio work in # DMT (computer monitor) modes #hdmi_drive=2 # uncomment to increase signal to HDMI, if you have interference, blanking, or # no display #config_hdmi_boost=4 # uncomment for composite PAL #sdtv_mode=2 #uncomment to overclock the arm. 700 MHz is the default. #arm_freq=800 # Uncomment some or all of these to enable the optional hardware interfaces #dtparam=i2c_arm=on #dtparam=i2s=on #dtparam=spi=on # Uncomment this to enable infrared communication. #dtoverlay=gpio-ir,gpio_pin=17 #dtoverlay=gpio-ir-tx,gpio_pin=18 # Additional overlays and parameters are documented /boot/overlays/README # Enable audio (loads snd_bcm2835) dtparam=audio=on [pi4] # Enable DRM VC4 V3D driver on top of the dispmanx display stack dtoverlay=vc4-fkms-v3d max_framebuffers=2 [all] #dtoverlay=vc4-fkms-v3d overscan_scale=1 #hdmi_max_pixel_freq:0=200000000 #hdmi_max_pixel_freq:1=200000000

@androidonpi I checked everything before screen savers and stuff like that all are off, sometimes when i have chromium open ublock crashes sometimes from what i saw before it happens.

When i log back in everything is closed. Could it be a pi 4 going bad at all, thats what has me worried a little.

@mitu I have a 1440p monitor and it doesn't work
Should I also add those lines?

@mitu I was overcomplicating the problem. Apparently I just needed to push the HDMI cable a little harder into the port. 🤣

The more you know. That probably should have been the first thing I tried, but thanks for the help!

@bberlin1 unfortunately you probably will have to

Far as I know, OMXolayer simply does not work together with game info displayed -- turn off one or both.

The remaining videos, it's almost certainly the video format. Use one of the scripts linked above to convert your existing videos. See this post to setup Skyscraper to detect and convert wrong-format videos on initial download, for future scrapes.

@dankcushions Thank you very much for the clarification! I guess my original problem is solved now.

@mitu I was just messing around with all of this. I don't have a RP4 yet, but plan to get one. I just wanted to get familiar with the different gaming-centric OSes before I got mine. I'm running this on a laptop that's running Windows 10. I need the ability to have Windows 10 running while I play around with this RP and emu stuff for the time-being. Using VirtualBox gives me that ability. I checked the '3D Acceleration' checkbox and now RetroPie runs. However it's really slow and beyond the configuration menu, I don't see anything else. I've got a VM that only loads an SD card (no 'host' VM OS) of another gaming front-end and the speed of it is great. I'm guessing the slowness has to do with running a system in a system in a VM (or something like that). That's cool. I just wanted to see it.

lrbarrios

@dankcushions looks works fine in Colin Mcrae Rally 2 when widgets are off.

@pjft i hear you but there must be a diferrence in the dev code
as 2.9.4 installed handles extensions ok
but dev not and its just the binary changed

I havent looked more into the ES dev as i have removed it when discovered the extension prob and needed to work on something else.
Latest weird thing happens now , is that video snaps dont play sound unless OMX HW is enabled. Videoscreensaver has no sound whatever i tried. I m using 2.9.3 at the moments as its the last ES that I can start the game from VSCR.

Im checking one at a time but everytime something fixed something else happens. I have latest OS updates, April FW
Ill post more. I ll put back 2.9.6 to do more testing on the sound things

PS i ll test more ES dev but that extensions prob displays rom counts and roms incorrectly

@thorr69 Yep, they're all in there. :-/

@yfzdude thank you for replying, I feel that I do have to research/find other methods of transferring ROMs to my Pi/RetroPie though than this flashdrive, because frankly I've had more flashdrives fail than MicroSDs! (blame the amount of moving parts I guess...).

@iandaemon @mitu
Booting into terminal fixed the problem and the games worked.
Thank you for the help 🙏

@tzinck the link I shared mentioned how to retrieve the verbose log.

@nemo93 Technically neither have I. It runs as a CD32 game if you rename the .CUE file. I've been running it like this for a while but 3.3 (or maybe an earlier version) seems to have broken it,

I'll wait to see what 3.4 brings.

@kikus said in lr-pcsx-rearmed loads but freezes at "Paused." black screen:

Built From: Started from Nachos 64GB image but updated all package from source recently

We don't support 3rd party images. Ask the author(s) of the image for support or use the image from retropie.org.uk/download.

@amook11

I had the same problem and with my pi in the network and under

\\retropie\configs\amiga\amiberry\conf\

I opened and edited this file:
rp-a500.uae
it has a line:

kickstart_rom_file

there goes the exact name of your 1.3 rom in the bios folder.
of course you can also rename your existing rom to name that's already there.

same procedure needs to be done for the 3.1 kickstart I 've just noticed..

for people unsure about the correct roms: https://github.com/midwan/amiberry/wiki/Kickstart-ROMs-(BIOS) there you can find information about the versions needed including a crc check code, to see if you've got the right file.